feat: generate mobile replays for local dev #19228
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Size Change: 0 B Total Size: 1.83 MB ℹ️ View Unchanged
|
This reverts commit 31960cf.
|
sometimes I despair of my own foolishness - this is what exported file playback is for 🙈 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We can't be all messaging Manoel and asking for him to send recordings into PostHog, that won't scale 🙃
For now this dumps one fixed recording into local storage
Later let's extend this to be a little more flexible, for now it meant I could figure out why SVG placeholders weren't correct without needing to push every intermediate attempt to production.
You can now run
DEBUG=1 python3 manage.py generate_mobile_replay_demo_dataand you get a single mobile replay added to your dev environmentTODO